Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7ae3664335fae51b63128b479f9b521e9a371a631f9691d66ee20103aa68a2

Tx prefix hash: fd4f7e7e82b7dbe79ffef47cd5bd40cb526856fb24debe67692689f08ee2215e
Tx public key: 73fe9762b1a2f5082a03146b5b0b636c55a902f74ceb797a82692347c2092bf2
Timestamp: 1709450681 Timestamp [UCT]: 2024-03-03 07:24:41 Age [y:d:h:m:s]: 01:023:07:33:40
Block: 970098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277643 RingCT/type: yes/0
Extra: 0173fe9762b1a2f5082a03146b5b0b636c55a902f74ceb797a82692347c2092bf20211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e15f91691450f1c7d351172bac6d14cc6024d2deeab711c4c7f2852c7db9c22 0.600000000000 1429947 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": 970108, "vin": [ { "gen": { "height": 970098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e15f91691450f1c7d351172bac6d14cc6024d2deeab711c4c7f2852c7db9c22" } } ], "extra": [ 1, 115, 254, 151, 98, 177, 162, 245, 8, 42, 3, 20, 107, 91, 11, 99, 108, 85, 169, 2, 247, 76, 235, 121, 122, 130, 105, 35, 71, 194, 9, 43, 242, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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