Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcb52f3dffe2bf73414fc36aa64171b622e6280aa723f56dc63e44147838ca9c

Tx prefix hash: d4657c0d7d1fb1c665e514dfcca585382c9b2308c0dd28af3cb64328861ca8c1
Tx public key: 78fd85bf4fddf67c7a779390ee7f92915c06f2a349d93aa145cdfc3d60a79e23
Timestamp: 1726593780 Timestamp [UCT]: 2024-09-17 17:23:00 Age [y:d:h:m:s]: 00:211:08:53:34
Block: 1112215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150902 RingCT/type: yes/0
Extra: 0178fd85bf4fddf67c7a779390ee7f92915c06f2a349d93aa145cdfc3d60a79e23021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d464cb4adbf3a41ec38c8adc4abaa8190067ee87dd9635f601c7bc3e937c23d8 0.600000000000 1591458 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": 1112225, "vin": [ { "gen": { "height": 1112215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d464cb4adbf3a41ec38c8adc4abaa8190067ee87dd9635f601c7bc3e937c23d8" } } ], "extra": [ 1, 120, 253, 133, 191, 79, 221, 246, 124, 122, 119, 147, 144, 238, 127, 146, 145, 92, 6, 242, 163, 73, 217, 58, 161, 69, 205, 252, 61, 96, 167, 158, 35, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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