Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 009c272dd78f29338035197f80b9f9478ffb8997950bb4c22c27e79e2d814cb3

Tx prefix hash: 7cf5bedf815110b237b27152083d21d71e165fc531d754d502044974f682baf7
Tx public key: b0ca5d0fff12a9a73291f0d4f1220ef309a56411aafa086909b6d7ebe7c40fdd
Timestamp: 1697160425 Timestamp [UCT]: 2023-10-13 01:27:05 Age [y:d:h:m:s]: 01:099:15:32:51
Block: 868402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332439 RingCT/type: yes/0
Extra: 01b0ca5d0fff12a9a73291f0d4f1220ef309a56411aafa086909b6d7ebe7c40fdd02110000000133af99f4000000000000000000

1 output(s) for total of 0.813998703000 dcy

stealth address amount amount idx
00: 46117628ad87490fb4ecff0ae8772bd7453205dde6c813552b63145efa24d0ea 0.813998703000 1323209 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": 868412, "vin": [ { "gen": { "height": 868402 } } ], "vout": [ { "amount": 813998703, "target": { "key": "46117628ad87490fb4ecff0ae8772bd7453205dde6c813552b63145efa24d0ea" } } ], "extra": [ 1, 176, 202, 93, 15, 255, 18, 169, 167, 50, 145, 240, 212, 241, 34, 14, 243, 9, 165, 100, 17, 170, 250, 8, 105, 9, 182, 215, 235, 231, 196, 15, 221, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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