Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d142777ee2ca104a857e6490166c4a1ae8a85498c722f6d6974c3c005bb557d7

Tx prefix hash: 4bf38d89af747743d448f4a883235637c4a17f4b16805a0b826956acda2ae28a
Tx public key: bb1fd61e5737db8f105b10ce6f1407c97e1dbf53729c5a476c5c6fd5ec5fc1e1
Timestamp: 1749073591 Timestamp [UCT]: 2025-06-04 21:46:31 Age [y:d:h:m:s]: 00:217:18:04:53
Block: 1298048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153377 RingCT/type: yes/0
Extra: 01bb1fd61e5737db8f105b10ce6f1407c97e1dbf53729c5a476c5c6fd5ec5fc1e102110000000e43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4916c2efe8159d5377fbd9530f2ec2dcd54af64026f28da2c18e53d2dc135a06 0.600000000000 1785571 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": 1298058, "vin": [ { "gen": { "height": 1298048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4916c2efe8159d5377fbd9530f2ec2dcd54af64026f28da2c18e53d2dc135a06" } } ], "extra": [ 1, 187, 31, 214, 30, 87, 55, 219, 143, 16, 91, 16, 206, 111, 20, 7, 201, 126, 29, 191, 83, 114, 156, 90, 71, 108, 92, 111, 213, 236, 95, 193, 225, 2, 17, 0, 0, 0, 14, 67, 132, 109, 102, 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