Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7bdc4626dbd233f5956b225ea7389dae2449854799051bee9cd58423452bdeb

Tx prefix hash: 8b5af94d77f71d46c59a3c3abdad4a433e55ec98ea1bc4ef1c1e14e54738622b
Tx public key: a721252b3a215f2c12297ff9da5c326681a0e5437b31cd88aaf5efe0f7fc2e61
Timestamp: 1699748119 Timestamp [UCT]: 2023-11-12 00:15:19 Age [y:d:h:m:s]: 01:362:23:34:27
Block: 889661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518323 RingCT/type: yes/0
Extra: 01a721252b3a215f2c12297ff9da5c326681a0e5437b31cd88aaf5efe0f7fc2e6102110000000633af99f4000000000000000000

1 output(s) for total of 0.692123810000 dcy

stealth address amount amount idx
00: 2f96eb6c9248e2c5cc4238046b73f0b787db7fed4bd35e5c18441d41bb3d39be 0.692123810000 1345670 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": 889671, "vin": [ { "gen": { "height": 889661 } } ], "vout": [ { "amount": 692123810, "target": { "key": "2f96eb6c9248e2c5cc4238046b73f0b787db7fed4bd35e5c18441d41bb3d39be" } } ], "extra": [ 1, 167, 33, 37, 43, 58, 33, 95, 44, 18, 41, 127, 249, 218, 92, 50, 102, 129, 160, 229, 67, 123, 49, 205, 136, 170, 245, 239, 224, 247, 252, 46, 97, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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