Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2889f1e42f354d3d58c2084acdc2d4432c63c676b9b2c90d6832c6947bcbe17a

Tx prefix hash: d7be2d5d1fe07b4de04e317814bb11509360097066d646af1ace15ff5f6d4128
Tx public key: 8cb840c88ea0c273b875ba86d07844776603f856ae45a027f61ec9707bc54727
Timestamp: 1728317090 Timestamp [UCT]: 2024-10-07 16:04:50 Age [y:d:h:m:s]: 00:199:16:55:29
Block: 1126508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142536 RingCT/type: yes/0
Extra: 018cb840c88ea0c273b875ba86d07844776603f856ae45a027f61ec9707bc54727021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e8857bbf94af088eb6fb0634f462c0ab8aa356c1feeaf8a023072c5449015e1 0.600000000000 1609303 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": 1126518, "vin": [ { "gen": { "height": 1126508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e8857bbf94af088eb6fb0634f462c0ab8aa356c1feeaf8a023072c5449015e1" } } ], "extra": [ 1, 140, 184, 64, 200, 142, 160, 194, 115, 184, 117, 186, 134, 208, 120, 68, 119, 102, 3, 248, 86, 174, 69, 160, 39, 246, 30, 201, 112, 123, 197, 71, 39, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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