Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e9af90b3da566011b9769b360d3a0a873c557ec86a5f7d486eaff1d37f492f6

Tx prefix hash: 4b358bf1f38303f7997a07acf9bbc10ac01a6e105936f05625e857793ec45611
Tx public key: beab24d4de38c7d82dfff895612a8ad22cb5f827b9d0396dcf2d383e75d7b0f0
Timestamp: 1587897661 Timestamp [UCT]: 2020-04-26 10:41:01 Age [y:d:h:m:s]: 05:192:14:19:42
Block: 96746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1307695 RingCT/type: yes/0
Extra: 01beab24d4de38c7d82dfff895612a8ad22cb5f827b9d0396dcf2d383e75d7b0f00211000002d560e3cc90000000000000000000

1 output(s) for total of 293.387162933000 dcy

stealth address amount amount idx
00: 7a4fbf97bc495eb85ef4d0e8db8a2d5fad1c0a31f64000b907b98bbd9a72199c 293.387162933000 171453 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": 96756, "vin": [ { "gen": { "height": 96746 } } ], "vout": [ { "amount": 293387162933, "target": { "key": "7a4fbf97bc495eb85ef4d0e8db8a2d5fad1c0a31f64000b907b98bbd9a72199c" } } ], "extra": [ 1, 190, 171, 36, 212, 222, 56, 199, 216, 45, 255, 248, 149, 97, 42, 138, 210, 44, 181, 248, 39, 185, 208, 57, 109, 207, 45, 56, 62, 117, 215, 176, 240, 2, 17, 0, 0, 2, 213, 96, 227, 204, 144, 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