Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c12680f0ab15c12373b1616c4950ba1d6204155aca4e3b7100daad597f4671fd

Tx prefix hash: 2ea3f39ba5c13245e87264d4d69d0c29403e1c5500783df3070438611f0ed1f3
Tx public key: d0753cfa29801ac394be6dd7a739977c3f43fcb4cd4c2c053700420928ff671c
Timestamp: 1701529416 Timestamp [UCT]: 2023-12-02 15:03:36 Age [y:d:h:m:s]: 01:044:07:23:54
Block: 904417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293049 RingCT/type: yes/0
Extra: 01d0753cfa29801ac394be6dd7a739977c3f43fcb4cd4c2c053700420928ff671c02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.618430663000 dcy

stealth address amount amount idx
00: 48bd98e68e2875798baa8edbd1b7e041a8c50f9b197a4bdd23ede41c3795b669 0.618430663000 1361168 of 0

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": 904427, "vin": [ { "gen": { "height": 904417 } } ], "vout": [ { "amount": 618430663, "target": { "key": "48bd98e68e2875798baa8edbd1b7e041a8c50f9b197a4bdd23ede41c3795b669" } } ], "extra": [ 1, 208, 117, 60, 250, 41, 128, 26, 195, 148, 190, 109, 215, 167, 57, 151, 124, 63, 67, 252, 180, 205, 76, 44, 5, 55, 0, 66, 9, 40, 255, 103, 28, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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