Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b71001699557d3e55f64dda1644dead0f0ff3e6863744d3eed5d6007ff4186

Tx prefix hash: d10fd8db6268d9d3805d635cc4948de392f30b6b71593695e1b0261e6fc48118
Tx public key: fedbbf983855c8efe83eecaac2ea82b33ec18f0de81f4e831739f4b5f8f0f44d
Timestamp: 1714909978 Timestamp [UCT]: 2024-05-05 11:52:58 Age [y:d:h:m:s]: 00:347:19:27:10
Block: 1015366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248621 RingCT/type: yes/0
Extra: 01fedbbf983855c8efe83eecaac2ea82b33ec18f0de81f4e831739f4b5f8f0f44d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: 333e5c74bc63cc01b16484e48efb44bca60bac8d02009e1ae4c1f28de7070efe 0.615600000000 1478707 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": 1015376, "vin": [ { "gen": { "height": 1015366 } } ], "vout": [ { "amount": 615600000, "target": { "key": "333e5c74bc63cc01b16484e48efb44bca60bac8d02009e1ae4c1f28de7070efe" } } ], "extra": [ 1, 254, 219, 191, 152, 56, 85, 200, 239, 232, 62, 236, 170, 194, 234, 130, 179, 62, 193, 143, 13, 232, 31, 78, 131, 23, 57, 244, 181, 248, 240, 244, 77, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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