Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22053d5d473400fb17b8fd17fbe864ed964317a1b7aa30ca409966e2e40d16ab

Tx prefix hash: b53cd406529a20a83cdbae946a3e789a4f184c24f09b33f683f5ccf9dd5b7c91
Tx public key: 6d4a9b6fef589b48b0ea64bb7bc9aaf37ebbffdb33684d082a1e652d84297970
Timestamp: 1738245467 Timestamp [UCT]: 2025-01-30 13:57:47 Age [y:d:h:m:s]: 00:138:01:13:50
Block: 1208397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98637 RingCT/type: yes/0
Extra: 016d4a9b6fef589b48b0ea64bb7bc9aaf37ebbffdb33684d082a1e652d842979700211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3dfa748c7f98cbbd403d66f5d2919d5ca6202a40e50652954ac170dc810e3a1 0.600000000000 1695128 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": 1208407, "vin": [ { "gen": { "height": 1208397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3dfa748c7f98cbbd403d66f5d2919d5ca6202a40e50652954ac170dc810e3a1" } } ], "extra": [ 1, 109, 74, 155, 111, 239, 88, 155, 72, 176, 234, 100, 187, 123, 201, 170, 243, 126, 187, 255, 219, 51, 104, 77, 8, 42, 30, 101, 45, 132, 41, 121, 112, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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