Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e12888657de9e87f91d7801f8ccc67941e403ae5b440d127dad0ca6da48ca77

Tx prefix hash: 06d355b5aaf4fb486ecc845339a96165975eb0404a653f6b7d3b38bdb54a59f0
Tx public key: 29aa863d95ded8d56a520ed7a932ad1b1ad0b2951537e5e5270618bb905b74c6
Timestamp: 1648664611 Timestamp [UCT]: 2022-03-30 18:23:31 Age [y:d:h:m:s]: 02:271:00:21:26
Block: 469756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 713303 RingCT/type: yes/0
Extra: 0129aa863d95ded8d56a520ed7a932ad1b1ad0b2951537e5e5270618bb905b74c6021100000024d3fcec30000000000000000000

1 output(s) for total of 17.041335114000 dcy

stealth address amount amount idx
00: 767639fc1510539b3e5f6b5608a2abc0fae1416d25d1b3110651baf0ef776268 17.041335114000 888760 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": 469766, "vin": [ { "gen": { "height": 469756 } } ], "vout": [ { "amount": 17041335114, "target": { "key": "767639fc1510539b3e5f6b5608a2abc0fae1416d25d1b3110651baf0ef776268" } } ], "extra": [ 1, 41, 170, 134, 61, 149, 222, 216, 213, 106, 82, 14, 215, 169, 50, 173, 27, 26, 208, 178, 149, 21, 55, 229, 229, 39, 6, 24, 187, 144, 91, 116, 198, 2, 17, 0, 0, 0, 36, 211, 252, 236, 48, 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