Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34f4abcf4dfdbccaedf0f8fad8b4f3880b1928b422004e1f0012ecbecad90f74

Tx prefix hash: fff3cd40a6e8bb05aea4298795f58936fda52ec6ac12d149354b32983f4ac4ac
Tx public key: ffb4e5ae9eb74f703def7fefbd1edb594f9168950fa7cc1d161be3759f2c8595
Timestamp: 1735686989 Timestamp [UCT]: 2024-12-31 23:16:29 Age [y:d:h:m:s]: 00:303:07:35:53
Block: 1187476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214286 RingCT/type: yes/0
Extra: 01ffb4e5ae9eb74f703def7fefbd1edb594f9168950fa7cc1d161be3759f2c85950211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9b507d68b50ef21e481ea2e381f1094df3f1a75586efee2e65997969c3408d4 0.600000000000 1673967 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": 1187486, "vin": [ { "gen": { "height": 1187476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9b507d68b50ef21e481ea2e381f1094df3f1a75586efee2e65997969c3408d4" } } ], "extra": [ 1, 255, 180, 229, 174, 158, 183, 79, 112, 61, 239, 127, 239, 189, 30, 219, 89, 79, 145, 104, 149, 15, 167, 204, 29, 22, 27, 227, 117, 159, 44, 133, 149, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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