Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7338054ef22c7eae8743efac8f8b595667aac6f828e91b1bf9a8342d2c25fc6

Tx prefix hash: f50c0d678b095d65c26068925e93338b9012dc7599f8321f86c8481897e0c8eb
Tx public key: 3bb31abc2e8b1f4b141e5dc614ca7d01ad4a651b5dcd39022322a8aff71afd80
Timestamp: 1730831023 Timestamp [UCT]: 2024-11-05 18:23:43 Age [y:d:h:m:s]: 00:151:20:53:42
Block: 1147257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108367 RingCT/type: yes/0
Extra: 013bb31abc2e8b1f4b141e5dc614ca7d01ad4a651b5dcd39022322a8aff71afd80021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6326f44396b6a4820bacd0346680a3dae24633dfad1341ec52db2af37f65b9fd 0.600000000000 1631952 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": 1147267, "vin": [ { "gen": { "height": 1147257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6326f44396b6a4820bacd0346680a3dae24633dfad1341ec52db2af37f65b9fd" } } ], "extra": [ 1, 59, 179, 26, 188, 46, 139, 31, 75, 20, 30, 93, 198, 20, 202, 125, 1, 173, 74, 101, 27, 93, 205, 57, 2, 35, 34, 168, 175, 247, 26, 253, 128, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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