Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc0239a4cb3c325c7908e93c73e5634fa28ad601d4c680ce7048ce85f167727b

Tx prefix hash: 172594fbd272a20c9eb4da6d73b5192e06a596cd5e3d9a5e1cb4a3fd49d72dc9
Tx public key: 89ed80dd2c4195edfdcefde78c31f0a41a5860dbbaa0b3d241c1aeb8f04e33a1
Timestamp: 1728127821 Timestamp [UCT]: 2024-10-05 11:30:21 Age [y:d:h:m:s]: 00:202:04:10:12
Block: 1124939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144308 RingCT/type: yes/0
Extra: 0189ed80dd2c4195edfdcefde78c31f0a41a5860dbbaa0b3d241c1aeb8f04e33a102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3907baa1404b02e609b6e0d91cb524b09d1e0be56076b617a24d8e808fec00d4 0.600000000000 1607612 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": 1124949, "vin": [ { "gen": { "height": 1124939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3907baa1404b02e609b6e0d91cb524b09d1e0be56076b617a24d8e808fec00d4" } } ], "extra": [ 1, 137, 237, 128, 221, 44, 65, 149, 237, 253, 206, 253, 231, 140, 49, 240, 164, 26, 88, 96, 219, 186, 160, 179, 210, 65, 193, 174, 184, 240, 78, 51, 161, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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