Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ada4271a0afa9deb07cb1b9d91013f2b751b77618769fd52035ac4a97ec8ab6

Tx prefix hash: 899b843ac4049c1bb5b9a8f7160369ace1d3fa97e8b23d3065af1f2ad8fc3d9a
Tx public key: f9df3d5b5d1dba8a049381c4b55f64a1494664924a9743cb47df9fcd566c72b8
Timestamp: 1697363811 Timestamp [UCT]: 2023-10-15 09:56:51 Age [y:d:h:m:s]: 01:163:04:58:10
Block: 870095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377645 RingCT/type: yes/0
Extra: 01f9df3d5b5d1dba8a049381c4b55f64a1494664924a9743cb47df9fcd566c72b802110000001275e3f0e9000000000000000000

1 output(s) for total of 0.803552208000 dcy

stealth address amount amount idx
00: 01f90a6f34c340d75a49f0a37b997ed28be7e04a33dc14f4d1253597d147dc85 0.803552208000 1324968 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": 870105, "vin": [ { "gen": { "height": 870095 } } ], "vout": [ { "amount": 803552208, "target": { "key": "01f90a6f34c340d75a49f0a37b997ed28be7e04a33dc14f4d1253597d147dc85" } } ], "extra": [ 1, 249, 223, 61, 91, 93, 29, 186, 138, 4, 147, 129, 196, 181, 95, 100, 161, 73, 70, 100, 146, 74, 151, 67, 203, 71, 223, 159, 205, 86, 108, 114, 184, 2, 17, 0, 0, 0, 18, 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