Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f4aa94d2d4b765129fd7c15ea64e22150605489e721cbace5d7bd3c0aeba91

Tx prefix hash: e0dadce8fc9676673df71df84b827a711d12dc1f136af3f7a9e1e9cb82d941b8
Tx public key: a1d247b0eebd5f09b757886fb1ed87cd20015994e5c5fdd123ee8d6754ba2e79
Timestamp: 1715324800 Timestamp [UCT]: 2024-05-10 07:06:40 Age [y:d:h:m:s]: 00:249:03:00:34
Block: 1018798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178305 RingCT/type: yes/0
Extra: 01a1d247b0eebd5f09b757886fb1ed87cd20015994e5c5fdd123ee8d6754ba2e790211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 037d837179705bb4b22ddf71d0c08d694e435a9dd685dc7c8296b7708a46087a 0.600000000000 1482593 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": 1018808, "vin": [ { "gen": { "height": 1018798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "037d837179705bb4b22ddf71d0c08d694e435a9dd685dc7c8296b7708a46087a" } } ], "extra": [ 1, 161, 210, 71, 176, 238, 189, 95, 9, 183, 87, 136, 111, 177, 237, 135, 205, 32, 1, 89, 148, 229, 197, 253, 209, 35, 238, 141, 103, 84, 186, 46, 121, 2, 17, 0, 0, 0, 5, 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