Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a1731f04c179c2ee5ae06d2b7fccc1b526033652b9663baea0ce7ab74955c20

Tx prefix hash: b9a894139f949927ce29117eda875baa8c916efcadf08ec9ad0e21f282a057ff
Tx public key: ae529fab2c9d97f5f6c5988ef10139135e33424f2f18c0222a2d30f29a21809f
Timestamp: 1759368198 Timestamp [UCT]: 2025-10-02 01:23:18 Age [y:d:h:m:s]: 00:095:22:32:45
Block: 1380807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68732 RingCT/type: yes/0
Extra: 01ae529fab2c9d97f5f6c5988ef10139135e33424f2f18c0222a2d30f29a21809f021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e848b573e8079c2726348f3403b1810cee01c79a11c602c95bd53284508ba543 0.600000000000 1868918 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": 1380817, "vin": [ { "gen": { "height": 1380807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e848b573e8079c2726348f3403b1810cee01c79a11c602c95bd53284508ba543" } } ], "extra": [ 1, 174, 82, 159, 171, 44, 157, 151, 245, 246, 197, 152, 142, 241, 1, 57, 19, 94, 51, 66, 79, 47, 24, 192, 34, 42, 45, 48, 242, 154, 33, 128, 159, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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