Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebeadbf4c545e976b4c9759f4f124939a8ca0363e39eb2ba090b499d83148885

Tx prefix hash: 973ec8ea80ba555affc2ce77a76afc219063ff51da9a43a6a2a2a5113d4e8894
Tx public key: 837036e4b2db0ed8dabb0db6d4e35bb8c42ab843ff2e0bbc7ff6684a5ababf3b
Timestamp: 1760568413 Timestamp [UCT]: 2025-10-15 22:46:53 Age [y:d:h:m:s]: 00:025:21:00:12
Block: 1390770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18528 RingCT/type: yes/0
Extra: 01837036e4b2db0ed8dabb0db6d4e35bb8c42ab843ff2e0bbc7ff6684a5ababf3b0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42c16627805ddbdb779253a90bc81bed52cfa10d2b81fdc21c2ba0a770b7458f 0.600000000000 1879017 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": 1390780, "vin": [ { "gen": { "height": 1390770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42c16627805ddbdb779253a90bc81bed52cfa10d2b81fdc21c2ba0a770b7458f" } } ], "extra": [ 1, 131, 112, 54, 228, 178, 219, 14, 216, 218, 187, 13, 182, 212, 227, 91, 184, 196, 42, 184, 67, 255, 46, 11, 188, 127, 246, 104, 74, 90, 186, 191, 59, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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