Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35d4cb1891aa1626ae523dae7030c4316439c31c67a526754988374ccd24335c

Tx prefix hash: 477b5fd79f6c5f257aca27ed5a891a260473c7bbf3c57236141039089e0759b1
Tx public key: a927ad4fa36a3fed66aacaa44f490301c79b16109ebf91d2485b1fb2c94b8cdd
Timestamp: 1702224092 Timestamp [UCT]: 2023-12-10 16:01:32 Age [y:d:h:m:s]: 01:195:07:38:14
Block: 910179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400573 RingCT/type: yes/0
Extra: 01a927ad4fa36a3fed66aacaa44f490301c79b16109ebf91d2485b1fb2c94b8cdd02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a07ec33520e646b92b3cabe01de2b5a3e312661a0110bc4e4a4face4d370d34 0.600000000000 1367324 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": 910189, "vin": [ { "gen": { "height": 910179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a07ec33520e646b92b3cabe01de2b5a3e312661a0110bc4e4a4face4d370d34" } } ], "extra": [ 1, 169, 39, 173, 79, 163, 106, 63, 237, 102, 170, 202, 164, 79, 73, 3, 1, 199, 155, 22, 16, 158, 191, 145, 210, 72, 91, 31, 178, 201, 75, 140, 221, 2, 17, 0, 0, 0, 2, 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