Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e23004e426f4644d46502d824f562900749acfb68401ec294703c4679583be76

Tx prefix hash: 4347505154340b745708413eee1d524e0c6ab316f2efa29b8153476f0aa305a1
Tx public key: 8db25b1989a2b4ee3a30e639f066a84f9e5c8fdcc551cf2090a4a420c466c7d2
Timestamp: 1694817069 Timestamp [UCT]: 2023-09-15 22:31:09 Age [y:d:h:m:s]: 01:129:22:26:44
Block: 848962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354137 RingCT/type: yes/0
Extra: 018db25b1989a2b4ee3a30e639f066a84f9e5c8fdcc551cf2090a4a420c466c7d202110000000a4b8f5122000000000000000000

1 output(s) for total of 0.944140291000 dcy

stealth address amount amount idx
00: 8e5c320b35d0d9aae28c33881d3b86751a267c0537a0fd637078fa04ba608783 0.944140291000 1302598 of 0

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": 848972, "vin": [ { "gen": { "height": 848962 } } ], "vout": [ { "amount": 944140291, "target": { "key": "8e5c320b35d0d9aae28c33881d3b86751a267c0537a0fd637078fa04ba608783" } } ], "extra": [ 1, 141, 178, 91, 25, 137, 162, 180, 238, 58, 48, 230, 57, 240, 102, 168, 79, 158, 92, 143, 220, 197, 81, 207, 32, 144, 164, 164, 32, 196, 102, 199, 210, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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