Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 567c0b6aa1a283258fa7de30076b8b0ae98850b87ddf7111c2b2383663b38267

Tx prefix hash: 0ff69e90c698370881650d2d23823006294f5b7c93eb3555ebb0d3a6c04bf1ad
Tx public key: 27bf9d911e49cbf3ceaf2305cc2b3614a6b8d3be17cafd607ae58aeaacf5f68c
Timestamp: 1663946153 Timestamp [UCT]: 2022-09-23 15:15:53 Age [y:d:h:m:s]: 02:053:03:11:02
Block: 594173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559532 RingCT/type: yes/0
Extra: 0127bf9d911e49cbf3ceaf2305cc2b3614a6b8d3be17cafd607ae58aeaacf5f68c02110000000275e3f0e9000000000000000000

1 output(s) for total of 6.595660096000 dcy

stealth address amount amount idx
00: ec9d1a44c4b07ca4dd10473e8be4dcddcf051f455b5d440a04ab1db1c885ed3d 6.595660096000 1029032 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": 594183, "vin": [ { "gen": { "height": 594173 } } ], "vout": [ { "amount": 6595660096, "target": { "key": "ec9d1a44c4b07ca4dd10473e8be4dcddcf051f455b5d440a04ab1db1c885ed3d" } } ], "extra": [ 1, 39, 191, 157, 145, 30, 73, 203, 243, 206, 175, 35, 5, 204, 43, 54, 20, 166, 184, 211, 190, 23, 202, 253, 96, 122, 229, 138, 234, 172, 245, 246, 140, 2, 17, 0, 0, 0, 2, 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