Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23c944e6ad0294acab3e0c7cd6421f3cd1257c579e1618fff1405887e2f34d30

Tx prefix hash: e442d1f3fee33c053a1478a25626d7700b1f2f76264b78adf2eaa6ddbe3f246e
Tx public key: d6fbf409b5e8e9f5753829615f7d521a7b2bfa9f959e6c8b0747acb3f2216570
Timestamp: 1726894354 Timestamp [UCT]: 2024-09-21 04:52:34 Age [y:d:h:m:s]: 00:174:21:10:15
Block: 1114710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124822 RingCT/type: yes/0
Extra: 01d6fbf409b5e8e9f5753829615f7d521a7b2bfa9f959e6c8b0747acb3f221657002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99edee5c9c3f4a5038c2378cdc2618b51407877e89a045ac504abdf7be8044ea 0.600000000000 1594587 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": 1114720, "vin": [ { "gen": { "height": 1114710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99edee5c9c3f4a5038c2378cdc2618b51407877e89a045ac504abdf7be8044ea" } } ], "extra": [ 1, 214, 251, 244, 9, 181, 232, 233, 245, 117, 56, 41, 97, 95, 125, 82, 26, 123, 43, 250, 159, 149, 158, 108, 139, 7, 71, 172, 179, 242, 33, 101, 112, 2, 17, 0, 0, 0, 6, 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