Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d9a002f1f18469be5607cce60fdd8ecd4958fde2972ec9bc840203488b2f5a

Tx prefix hash: e48151ac221a8fb7081d962d85710a432be8065708feae614615c036075ae63e
Tx public key: 896042f51df2e47ec2f99da9e62cd47e4778deb3bfe7e7ea816da4148aac80da
Timestamp: 1723600056 Timestamp [UCT]: 2024-08-14 01:47:36 Age [y:d:h:m:s]: 01:087:22:28:08
Block: 1087403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321314 RingCT/type: yes/0
Extra: 01896042f51df2e47ec2f99da9e62cd47e4778deb3bfe7e7ea816da4148aac80da021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a6e9730a499131ccb8b25f4c4eeaa79f9775ea4119d1c8fccee204c77ef316c 0.600000000000 1562012 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": 1087413, "vin": [ { "gen": { "height": 1087403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a6e9730a499131ccb8b25f4c4eeaa79f9775ea4119d1c8fccee204c77ef316c" } } ], "extra": [ 1, 137, 96, 66, 245, 29, 242, 228, 126, 194, 249, 157, 169, 230, 44, 212, 126, 71, 120, 222, 179, 191, 231, 231, 234, 129, 109, 164, 20, 138, 172, 128, 218, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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