Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea29ca1044b964cbf8577ba4987f30a1e7ecb25d788980a6a60b642f98b1a8eb

Tx prefix hash: 80031b5dbf37adf10ace4f604cdb2208838e470b9ec5890f9ae9563c17a2f27b
Tx public key: 6031de21bd822914234546ebff8ce22a7dad1e47cab91ed2fa49e9c2e0afe9e6
Timestamp: 1694294608 Timestamp [UCT]: 2023-09-09 21:23:28 Age [y:d:h:m:s]: 01:216:02:52:42
Block: 844630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415558 RingCT/type: yes/0
Extra: 016031de21bd822914234546ebff8ce22a7dad1e47cab91ed2fa49e9c2e0afe9e602110000000e4b8f5122000000000000000000

1 output(s) for total of 0.975896146000 dcy

stealth address amount amount idx
00: 0da3fa2e746f0932cdd3e1c5d151d2726a255ba1dc68185c679d77010ba87b97 0.975896146000 1297950 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": 844640, "vin": [ { "gen": { "height": 844630 } } ], "vout": [ { "amount": 975896146, "target": { "key": "0da3fa2e746f0932cdd3e1c5d151d2726a255ba1dc68185c679d77010ba87b97" } } ], "extra": [ 1, 96, 49, 222, 33, 189, 130, 41, 20, 35, 69, 70, 235, 255, 140, 226, 42, 125, 173, 30, 71, 202, 185, 30, 210, 250, 73, 233, 194, 224, 175, 233, 230, 2, 17, 0, 0, 0, 14, 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