Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff12ed3e9ad07f780e84bf60c7b5f0d1c63cb38c88c814c1bd11f5cb6ae5558f

Tx prefix hash: 950b7db92947dffaa9be25f1cd01df7974262fc9209e20ff64a48d3a52c68d2a
Tx public key: 078bc35fe7252c9270ee46cbe82a58850820f507dfab26a9748d02ef83b361c0
Timestamp: 1683394948 Timestamp [UCT]: 2023-05-06 17:42:28 Age [y:d:h:m:s]: 01:346:13:12:03
Block: 754339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508912 RingCT/type: yes/0
Extra: 01078bc35fe7252c9270ee46cbe82a58850820f507dfab26a9748d02ef83b361c0021100000003e7ace25d000000000000000000

1 output(s) for total of 1.943398883000 dcy

stealth address amount amount idx
00: a0a286d7d9ea005be9b36999543195461f5dcf694b9af9e714fe9bc48b683aa2 1.943398883000 1202592 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": 754349, "vin": [ { "gen": { "height": 754339 } } ], "vout": [ { "amount": 1943398883, "target": { "key": "a0a286d7d9ea005be9b36999543195461f5dcf694b9af9e714fe9bc48b683aa2" } } ], "extra": [ 1, 7, 139, 195, 95, 231, 37, 44, 146, 112, 238, 70, 203, 232, 42, 88, 133, 8, 32, 245, 7, 223, 171, 38, 169, 116, 141, 2, 239, 131, 179, 97, 192, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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