Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf86804b176157b0badd06a2e8b4d3e43ad1f85323d7c727412cd6adca50e0dd

Tx prefix hash: a2549967429ce9657a98a4f2c4298ee3c14ba769d9324bfd1880ebf1bf14684c
Tx public key: e912f8d65c6c8f35404113ba9aedf3153502dc41c868fb5fa0d4502a997f5de2
Timestamp: 1645685797 Timestamp [UCT]: 2022-02-24 06:56:37 Age [y:d:h:m:s]: 02:302:22:09:31
Block: 445320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735923 RingCT/type: yes/0
Extra: 01e912f8d65c6c8f35404113ba9aedf3153502dc41c868fb5fa0d4502a997f5de2021100000002a8c141c5000000000000000000

1 output(s) for total of 20.533844295000 dcy

stealth address amount amount idx
00: 6caf383d39ce410ac3da834bb9d06e542c54a639aa3e8be5d409d8f6e4e284b3 20.533844295000 858877 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": 445330, "vin": [ { "gen": { "height": 445320 } } ], "vout": [ { "amount": 20533844295, "target": { "key": "6caf383d39ce410ac3da834bb9d06e542c54a639aa3e8be5d409d8f6e4e284b3" } } ], "extra": [ 1, 233, 18, 248, 214, 92, 108, 143, 53, 64, 65, 19, 186, 154, 237, 243, 21, 53, 2, 220, 65, 200, 104, 251, 95, 160, 212, 80, 42, 153, 127, 93, 226, 2, 17, 0, 0, 0, 2, 168, 193, 65, 197, 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