Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78905115de6ddab9a9c50cdb193f7c17dcf2a4c0e2cfb648874322597e3980e3

Tx prefix hash: fe64a1617d8556b76e9fbad539184973c1e0053934e6cd790c98d446c83c1a5f
Tx public key: e254afbbe97d8a97c9b960abc8b896bbd47b375f94342b1eb36a305b5f585c84
Timestamp: 1731118188 Timestamp [UCT]: 2024-11-09 02:09:48 Age [y:d:h:m:s]: 00:170:19:07:04
Block: 1149654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121905 RingCT/type: yes/0
Extra: 01e254afbbe97d8a97c9b960abc8b896bbd47b375f94342b1eb36a305b5f585c84021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f6c2fea38ef2175e139a35d629400dc5bcb3619383eceb9812f2e98ecd158e 0.600000000000 1634781 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": 1149664, "vin": [ { "gen": { "height": 1149654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f6c2fea38ef2175e139a35d629400dc5bcb3619383eceb9812f2e98ecd158e" } } ], "extra": [ 1, 226, 84, 175, 187, 233, 125, 138, 151, 201, 185, 96, 171, 200, 184, 150, 187, 212, 123, 55, 95, 148, 52, 43, 30, 179, 106, 48, 91, 95, 88, 92, 132, 2, 17, 0, 0, 0, 1, 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