Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6fc3f11498b1b7e48f0f7f360605e552d76342cab284159e1121f8c348b9942

Tx prefix hash: 0856f177c6b1c05a92e333117e7ad377a1fb7d165ac48e6d95993aa2124f3b51
Tx public key: 5bc8d39b038937ec711cb39d5f6018b0e720af510a6a4dbf4ca78909ae8c0f7c
Timestamp: 1673570451 Timestamp [UCT]: 2023-01-13 00:40:51 Age [y:d:h:m:s]: 02:137:14:55:12
Block: 673492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620079 RingCT/type: yes/0
Extra: 015bc8d39b038937ec711cb39d5f6018b0e720af510a6a4dbf4ca78909ae8c0f7c0211000000068b7b6602000000000000000000

1 output(s) for total of 3.601151366000 dcy

stealth address amount amount idx
00: fc8205647d120aa8bf0d2affe2f6f27d95047be44b973e3bcca5d7ae1935ae3a 3.601151366000 1115105 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": 673502, "vin": [ { "gen": { "height": 673492 } } ], "vout": [ { "amount": 3601151366, "target": { "key": "fc8205647d120aa8bf0d2affe2f6f27d95047be44b973e3bcca5d7ae1935ae3a" } } ], "extra": [ 1, 91, 200, 211, 155, 3, 137, 55, 236, 113, 28, 179, 157, 95, 96, 24, 176, 231, 32, 175, 81, 10, 106, 77, 191, 76, 167, 137, 9, 174, 140, 15, 124, 2, 17, 0, 0, 0, 6, 139, 123, 102, 2, 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