Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc3f0689716c5079e882af30155f4a04442c8c90ca4b074153131abaa9ce82c3

Tx prefix hash: b101313c8fdbd3b2854f8f16d59d7f1d7a45f617917f0cb302fd1b120d798cc5
Tx public key: a65ecabe95bb344ae979c1eeeba6b18b42d4cd9d52339cacb438660ccae08fbd
Timestamp: 1681764334 Timestamp [UCT]: 2023-04-17 20:45:34 Age [y:d:h:m:s]: 02:227:17:38:10
Block: 740799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 682664 RingCT/type: yes/0
Extra: 01a65ecabe95bb344ae979c1eeeba6b18b42d4cd9d52339cacb438660ccae08fbd021100000004faf35c9c000000000000000000

1 output(s) for total of 2.154892499000 dcy

stealth address amount amount idx
00: ac5215f0c840e91c26d693afb1e443826692dfbfb877eeec9a2e208b1a116e05 2.154892499000 1187704 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": 740809, "vin": [ { "gen": { "height": 740799 } } ], "vout": [ { "amount": 2154892499, "target": { "key": "ac5215f0c840e91c26d693afb1e443826692dfbfb877eeec9a2e208b1a116e05" } } ], "extra": [ 1, 166, 94, 202, 190, 149, 187, 52, 74, 233, 121, 193, 238, 235, 166, 177, 139, 66, 212, 205, 157, 82, 51, 156, 172, 180, 56, 102, 12, 202, 224, 143, 189, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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