Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63466480cb3f757e4ffee37f1d0e0222ae7352cc6bfc5a63839012cbda20a9a4

Tx prefix hash: 126d5dd40a8ab25d466ad480c0ac3b2ea1b50b40a07c1e6ab2d9bf3a3b90117a
Tx public key: 0bcb45ec187028908c95e10fedb0c4fb40dc8383d5f3b0207de50e8f2041a5d4
Timestamp: 1609224996 Timestamp [UCT]: 2020-12-29 06:56:36 Age [y:d:h:m:s]: 04:055:17:37:49
Block: 171255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1053167 RingCT/type: yes/0
Extra: 010bcb45ec187028908c95e10fedb0c4fb40dc8383d5f3b0207de50e8f2041a5d402110000054727e2517e000000000000000000

1 output(s) for total of 166.173496328000 dcy

stealth address amount amount idx
00: 3a035b077003445c2af07d18f5e14a10521ff633ed6e0f4e09388b6d8b7cc9f8 166.173496328000 322202 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": 171265, "vin": [ { "gen": { "height": 171255 } } ], "vout": [ { "amount": 166173496328, "target": { "key": "3a035b077003445c2af07d18f5e14a10521ff633ed6e0f4e09388b6d8b7cc9f8" } } ], "extra": [ 1, 11, 203, 69, 236, 24, 112, 40, 144, 140, 149, 225, 15, 237, 176, 196, 251, 64, 220, 131, 131, 213, 243, 176, 32, 125, 229, 14, 143, 32, 65, 165, 212, 2, 17, 0, 0, 5, 71, 39, 226, 81, 126, 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