Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef9b53209678e621bf55730ea4bbfaea0f25c5f7fbbd4641a34a6d4c1230ce5

Tx prefix hash: 10a7334a572c4747dfcf9b31f75199ff981cdb4746f2dbf56697316de8ae997f
Tx public key: 516a6d30d0e572a1e9177a6f3a4fb68f650a5e71786bec304221c5f4c55b51e6
Timestamp: 1712603845 Timestamp [UCT]: 2024-04-08 19:17:25 Age [y:d:h:m:s]: 01:035:14:33:35
Block: 996207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286455 RingCT/type: yes/0
Extra: 01516a6d30d0e572a1e9177a6f3a4fb68f650a5e71786bec304221c5f4c55b51e602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ba55bd6160c2e11556c7c36407350360e5d57e0cb1e2c6b615a23e568ad096c 0.600000000000 1456623 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": 996217, "vin": [ { "gen": { "height": 996207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ba55bd6160c2e11556c7c36407350360e5d57e0cb1e2c6b615a23e568ad096c" } } ], "extra": [ 1, 81, 106, 109, 48, 208, 229, 114, 161, 233, 23, 122, 111, 58, 79, 182, 143, 101, 10, 94, 113, 120, 107, 236, 48, 66, 33, 197, 244, 197, 91, 81, 230, 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