Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f376827358315783c84ede1f70a073ddad1c73f09dc290c22a74310aa0cee83

Tx prefix hash: f50f438d7730c5f61669646b95ad9add552e3dd463a61e62092c5e54acde6293
Tx public key: 64717a90ea08c40832b52d8ff259616b521ea6c3e37e4d5d4a05f0f472783f5a
Timestamp: 1703725416 Timestamp [UCT]: 2023-12-28 01:03:36 Age [y:d:h:m:s]: 01:319:21:53:30
Block: 922633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487470 RingCT/type: yes/0
Extra: 0164717a90ea08c40832b52d8ff259616b521ea6c3e37e4d5d4a05f0f472783f5a02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06ff1456d6ad30af557d496ffe2f2b572e906e6feac0dbf2015c166945c3d360 0.600000000000 1380337 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": 922643, "vin": [ { "gen": { "height": 922633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06ff1456d6ad30af557d496ffe2f2b572e906e6feac0dbf2015c166945c3d360" } } ], "extra": [ 1, 100, 113, 122, 144, 234, 8, 196, 8, 50, 181, 45, 143, 242, 89, 97, 107, 82, 30, 166, 195, 227, 126, 77, 93, 74, 5, 240, 244, 114, 120, 63, 90, 2, 17, 0, 0, 0, 14, 89, 218, 211, 245, 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