Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9f047f7feeb9e55ea76f915603be7863f6e9f91ac243aafe7a998e32884c0fb

Tx prefix hash: 510f63dc920fd9b4173f4a20a03605f642996130b7526ea399b37f2e92bf4b63
Tx public key: 7eb52fae058a615511900091bbd1f4118fd4fd43631cf89c4024635ed9249dc9
Timestamp: 1709890605 Timestamp [UCT]: 2024-03-08 09:36:45 Age [y:d:h:m:s]: 01:098:21:03:23
Block: 973753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331612 RingCT/type: yes/0
Extra: 017eb52fae058a615511900091bbd1f4118fd4fd43631cf89c4024635ed9249dc90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ef2f7a9b24cef6d4fc64cb507e7b42a29c42e3571f04fcb7b4b6082c018117f 0.600000000000 1433692 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": 973763, "vin": [ { "gen": { "height": 973753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ef2f7a9b24cef6d4fc64cb507e7b42a29c42e3571f04fcb7b4b6082c018117f" } } ], "extra": [ 1, 126, 181, 47, 174, 5, 138, 97, 85, 17, 144, 0, 145, 187, 209, 244, 17, 143, 212, 253, 67, 99, 28, 248, 156, 64, 36, 99, 94, 217, 36, 157, 201, 2, 17, 0, 0, 0, 1, 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