Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b113707371f32b9991c708430e3ce67b9f0bf7a067f7455b82ab8fbf54869a9a

Tx prefix hash: ea4a5d6e4df87832d66c534712dfb3cff6c1c7446da49c18ce6f71183e2cf6d9
Tx public key: ac348d0dd72638d103f8737295998588bd4ff36d1e9d7ad127c1225e4cedf8b3
Timestamp: 1685619027 Timestamp [UCT]: 2023-06-01 11:30:27 Age [y:d:h:m:s]: 01:225:13:27:39
Block: 772775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422619 RingCT/type: yes/0
Extra: 01ac348d0dd72638d103f8737295998588bd4ff36d1e9d7ad127c1225e4cedf8b302110000000133af99f4000000000000000000

1 output(s) for total of 1.688401777000 dcy

stealth address amount amount idx
00: c1cb5b702bfd9e71a79981d0be3c0dc18248d9f684e0abe0a24eb935f1acd913 1.688401777000 1222204 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": 772785, "vin": [ { "gen": { "height": 772775 } } ], "vout": [ { "amount": 1688401777, "target": { "key": "c1cb5b702bfd9e71a79981d0be3c0dc18248d9f684e0abe0a24eb935f1acd913" } } ], "extra": [ 1, 172, 52, 141, 13, 215, 38, 56, 209, 3, 248, 115, 114, 149, 153, 133, 136, 189, 79, 243, 109, 30, 157, 122, 209, 39, 193, 34, 94, 76, 237, 248, 179, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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