Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45bf9c9409a6439b5a4338a4ce5bce48b211fad564e206e4a84944a7fe9e2dc9

Tx prefix hash: df552bfa929c9f04cf6c40c1415ddf9e99417e5bee16aea107cc8efbc314072a
Tx public key: ea90815a4a8763cbb869a908b5c7f6060ad915cd3f401030f8b306b2cc55345a
Timestamp: 1736143210 Timestamp [UCT]: 2025-01-06 06:00:10 Age [y:d:h:m:s]: 00:086:16:14:09
Block: 1191272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61702 RingCT/type: yes/0
Extra: 01ea90815a4a8763cbb869a908b5c7f6060ad915cd3f401030f8b306b2cc55345a0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10f3aeccc10ae07feddb64b2ddc88de863d8a45380bc75c95906ca1151eda8e 0.600000000000 1677795 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": 1191282, "vin": [ { "gen": { "height": 1191272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10f3aeccc10ae07feddb64b2ddc88de863d8a45380bc75c95906ca1151eda8e" } } ], "extra": [ 1, 234, 144, 129, 90, 74, 135, 99, 203, 184, 105, 169, 8, 181, 199, 246, 6, 10, 217, 21, 205, 63, 64, 16, 48, 248, 179, 6, 178, 204, 85, 52, 90, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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