Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b550dad48205ce19600d99570d0c2bbc68fa91a6201a59c2d36026a11112347

Tx prefix hash: ff18b10ccb5780755ab56afad2f8c28bd31b278560284b337426a9e211056581
Tx public key: 0d74fb906192c5c00873c76ae7e1e5b4ff295a4e87a60c8d83a883c061d24f0e
Timestamp: 1711246483 Timestamp [UCT]: 2024-03-24 02:14:43 Age [y:d:h:m:s]: 01:017:01:32:27
Block: 985007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273153 RingCT/type: yes/0
Extra: 010d74fb906192c5c00873c76ae7e1e5b4ff295a4e87a60c8d83a883c061d24f0e0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68c4dd2c0587ca2c5cda6cd3161f2ca1de377eb082585d317760adfd85302210 0.600000000000 1445212 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": 985017, "vin": [ { "gen": { "height": 985007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68c4dd2c0587ca2c5cda6cd3161f2ca1de377eb082585d317760adfd85302210" } } ], "extra": [ 1, 13, 116, 251, 144, 97, 146, 197, 192, 8, 115, 199, 106, 231, 225, 229, 180, 255, 41, 90, 78, 135, 166, 12, 141, 131, 168, 131, 192, 97, 210, 79, 14, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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