Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 81e4dff027684c3f16436e10de94f0d18ff4dd6931c8d472cd62e8941c2e2801

Tx prefix hash: 42be6a5cfcf84cbf2843caff1d841be4c6d04cc1a0de18e6c5890cb6f36ffb47
Tx public key: e9d82aad100468963b7ea1a84801b851c7a2747a8a88af0a5b269ca6f3b0a6a9
Timestamp: 1722937755 Timestamp [UCT]: 2024-08-06 09:49:15 Age [y:d:h:m:s]: 00:116:23:31:11
Block: 1081907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83705 RingCT/type: yes/0
Extra: 01e9d82aad100468963b7ea1a84801b851c7a2747a8a88af0a5b269ca6f3b0a6a9021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b260fa5f10725295c0a48df4aa75fea88e04b2b69c6b241dd347cd7d5ee134 0.600000000000 1555730 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1081917, "vin": [ { "gen": { "height": 1081907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b260fa5f10725295c0a48df4aa75fea88e04b2b69c6b241dd347cd7d5ee134" } } ], "extra": [ 1, 233, 216, 42, 173, 16, 4, 104, 150, 59, 126, 161, 168, 72, 1, 184, 81, 199, 162, 116, 122, 138, 136, 175, 10, 91, 38, 156, 166, 243, 176, 166, 169, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8