Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7f0eae3a82932eb78fb1b1a0e393fcbc901231c682c3e97fea170f32341100

Tx prefix hash: 5b91742523811b8b316b93cc86c4ebec6a9ffdf3b425d1a5ba08e81621a0edaa
Tx public key: 8862dbec07c97925edb11c71713df2964f753c7c1127a34f59a51723ec49d250
Timestamp: 1736566330 Timestamp [UCT]: 2025-01-11 03:32:10 Age [y:d:h:m:s]: 00:157:14:51:15
Block: 1194751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112363 RingCT/type: yes/0
Extra: 018862dbec07c97925edb11c71713df2964f753c7c1127a34f59a51723ec49d250021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c7a97756fb0516c65d74da3eab43e4862eaf085ef13fa4f8bae316b13133b18 0.600000000000 1681328 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": 1194761, "vin": [ { "gen": { "height": 1194751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c7a97756fb0516c65d74da3eab43e4862eaf085ef13fa4f8bae316b13133b18" } } ], "extra": [ 1, 136, 98, 219, 236, 7, 201, 121, 37, 237, 177, 28, 113, 113, 61, 242, 150, 79, 117, 60, 124, 17, 39, 163, 79, 89, 165, 23, 35, 236, 73, 210, 80, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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