Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad528137534c559260e36999e69ecd63ee194d31fad8a31f2e59f99b8681cd41

Tx prefix hash: 918fbcab5f9a8b62f3faa23eb1d012b8b3cccaeffb9729af1f110714b3eef969
Tx public key: caff6a16f1e52ee2e884c815ba3b3348d989d0677276f0c6c942f5a430c698dd
Timestamp: 1681270422 Timestamp [UCT]: 2023-04-12 03:33:42 Age [y:d:h:m:s]: 02:003:12:36:33
Block: 736697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524688 RingCT/type: yes/0
Extra: 01caff6a16f1e52ee2e884c815ba3b3348d989d0677276f0c6c942f5a430c698dd021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.223398171000 dcy

stealth address amount amount idx
00: 8fddac16c6da485d407f6bc3635698b2bfe0506b8044a998479081efbf789f11 2.223398171000 1183160 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": 736707, "vin": [ { "gen": { "height": 736697 } } ], "vout": [ { "amount": 2223398171, "target": { "key": "8fddac16c6da485d407f6bc3635698b2bfe0506b8044a998479081efbf789f11" } } ], "extra": [ 1, 202, 255, 106, 22, 241, 229, 46, 226, 232, 132, 200, 21, 186, 59, 51, 72, 217, 137, 208, 103, 114, 118, 240, 198, 201, 66, 245, 164, 48, 198, 152, 221, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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