Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaec57cec7dbad468cb8c3a33f5535d9bb3e2428ceb3b7e9e3fd9484c02914c5

Tx prefix hash: cc8f66034ad173654b7d70e123da8fed14e17b367f86deb12f5e71eda54046e7
Tx public key: 7621c38adfe01bdea814a17b61b956891bd7d639ea4f3273e960d9f1981c72a9
Timestamp: 1746466946 Timestamp [UCT]: 2025-05-05 17:42:26 Age [y:d:h:m:s]: 00:001:05:08:12
Block: 1276464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 861 RingCT/type: yes/0
Extra: 017621c38adfe01bdea814a17b61b956891bd7d639ea4f3273e960d9f1981c72a90211000000071f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cc303e5a04938ce428b8c9a9744ce37f8b95c9ad065ea6a4ea51237fc51675f 0.600000000000 1763807 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": 1276474, "vin": [ { "gen": { "height": 1276464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cc303e5a04938ce428b8c9a9744ce37f8b95c9ad065ea6a4ea51237fc51675f" } } ], "extra": [ 1, 118, 33, 195, 138, 223, 224, 27, 222, 168, 20, 161, 123, 97, 185, 86, 137, 27, 215, 214, 57, 234, 79, 50, 115, 233, 96, 217, 241, 152, 28, 114, 169, 2, 17, 0, 0, 0, 7, 31, 144, 81, 122, 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