Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792326cdb852f4efa3b44c38773cc0b4cd3c5232d2b5887169dc982f86622a38

Tx prefix hash: 6b1369502d66235d75c6350a894fe23ae42b12a62a60fa3c050b3608da00f5a0
Tx public key: 4cc5471eb14478e50b24837b1dba3e13b9dd7c43c8744fa2ada9d253ca2f37f1
Timestamp: 1724977329 Timestamp [UCT]: 2024-08-30 00:22:09 Age [y:d:h:m:s]: 01:039:20:49:35
Block: 1098813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286887 RingCT/type: yes/0
Extra: 014cc5471eb14478e50b24837b1dba3e13b9dd7c43c8744fa2ada9d253ca2f37f1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b09236c20ccb29424d0fea60b50804e201a3672f2243266a78419b4b51a3867d 0.600000000000 1574656 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": 1098823, "vin": [ { "gen": { "height": 1098813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b09236c20ccb29424d0fea60b50804e201a3672f2243266a78419b4b51a3867d" } } ], "extra": [ 1, 76, 197, 71, 30, 177, 68, 120, 229, 11, 36, 131, 123, 29, 186, 62, 19, 185, 221, 124, 67, 200, 116, 79, 162, 173, 169, 210, 83, 202, 47, 55, 241, 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