Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d812b4eab536d65fa2da8a0199f75c37ad5e3cf62f55dbc9d788782a29dc62

Tx prefix hash: 2a3a18ae1d4a3cee3ea63a434401b820fd9301ec0ef42e30cc7472fa897b7764
Tx public key: 6f580095563776d0f34b67f9eebfaeb1a7cca847ab73d86f6abd3e44ff4eb0d9
Timestamp: 1673839796 Timestamp [UCT]: 2023-01-16 03:29:56 Age [y:d:h:m:s]: 02:093:19:46:36
Block: 675725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588743 RingCT/type: yes/0
Extra: 016f580095563776d0f34b67f9eebfaeb1a7cca847ab73d86f6abd3e44ff4eb0d9021100000001faf35c9c000000000000000000

1 output(s) for total of 3.540319988000 dcy

stealth address amount amount idx
00: fbed3dbedcb78e83490abc17a4e8ae57aae74ceb8bdf531e1b8314eb234593a7 3.540319988000 1117408 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": 675735, "vin": [ { "gen": { "height": 675725 } } ], "vout": [ { "amount": 3540319988, "target": { "key": "fbed3dbedcb78e83490abc17a4e8ae57aae74ceb8bdf531e1b8314eb234593a7" } } ], "extra": [ 1, 111, 88, 0, 149, 86, 55, 118, 208, 243, 75, 103, 249, 238, 191, 174, 177, 167, 204, 168, 71, 171, 115, 216, 111, 106, 189, 62, 68, 255, 78, 176, 217, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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