Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634872c6359a94ff40f1758ba3343859c6fe8b070f5155ff484cbcb29cc2068b

Tx prefix hash: 571e40fddd34fee2d2cd0f4dd2ee3ed3de20fb558c8270f8a74def92ec7f9a3c
Tx public key: 1a4dbb38b7d8a0571d46529ccc1b4d35795a4fd3faf3f39bac36e3b12ebb9ecc
Timestamp: 1635029528 Timestamp [UCT]: 2021-10-23 22:52:08 Age [y:d:h:m:s]: 03:064:23:03:59
Block: 359128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 824731 RingCT/type: yes/0
Extra: 011a4dbb38b7d8a0571d46529ccc1b4d35795a4fd3faf3f39bac36e3b12ebb9ecc0211000000158d0de867000000000000000000

1 output(s) for total of 39.635952779000 dcy

stealth address amount amount idx
00: f31cf95b063c065fd0016eced93e7e3d0bedcf0c60d0cd6bad187c2b71b79dfc 39.635952779000 731447 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": 359138, "vin": [ { "gen": { "height": 359128 } } ], "vout": [ { "amount": 39635952779, "target": { "key": "f31cf95b063c065fd0016eced93e7e3d0bedcf0c60d0cd6bad187c2b71b79dfc" } } ], "extra": [ 1, 26, 77, 187, 56, 183, 216, 160, 87, 29, 70, 82, 156, 204, 27, 77, 53, 121, 90, 79, 211, 250, 243, 243, 155, 172, 54, 227, 177, 46, 187, 158, 204, 2, 17, 0, 0, 0, 21, 141, 13, 232, 103, 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