Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a922331c2f3ac309c8d9612fafd0d262f4541596c1de959845264112221f21d

Tx prefix hash: b977caf813de14fc87d7cd3a362087bf180b4d52eb5981fa9d68b875556ea872
Tx public key: 45c8fee2d5d372b4cfc84443cbdb01b5d92c4a5be26b32699cfe667d7a9d94d7
Timestamp: 1698893758 Timestamp [UCT]: 2023-11-02 02:55:58 Age [y:d:h:m:s]: 01:150:10:03:16
Block: 882778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368502 RingCT/type: yes/0
Extra: 0145c8fee2d5d372b4cfc84443cbdb01b5d92c4a5be26b32699cfe667d7a9d94d702110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.729440775000 dcy

stealth address amount amount idx
00: 66f2f894557e3f3c4722d3ff1ffc9f65233938dcbe41369bb2f1e10ea6845b0a 0.729440775000 1338456 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": 882788, "vin": [ { "gen": { "height": 882778 } } ], "vout": [ { "amount": 729440775, "target": { "key": "66f2f894557e3f3c4722d3ff1ffc9f65233938dcbe41369bb2f1e10ea6845b0a" } } ], "extra": [ 1, 69, 200, 254, 226, 213, 211, 114, 180, 207, 200, 68, 67, 203, 219, 1, 181, 217, 44, 74, 91, 226, 107, 50, 105, 156, 254, 102, 125, 122, 157, 148, 215, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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