Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85c13927d4f83514e8fe8607f92f8cc53fc3ef8a7261e006afe2bc868581ddb7

Tx prefix hash: 533811d2f7bfd9e85e1030dd61644ee0bb42671d2a3ef91f3d79a332fc5ee667
Tx public key: 43873989d4c47e0db2e89d93f5c9d159f661feb1e5503942b9f2b47248ead881
Timestamp: 1648636068 Timestamp [UCT]: 2022-03-30 10:27:48 Age [y:d:h:m:s]: 02:350:04:59:27
Block: 469510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769700 RingCT/type: yes/0
Extra: 0143873989d4c47e0db2e89d93f5c9d159f661feb1e5503942b9f2b47248ead881021100000001cb8520c2000000000000000000

1 output(s) for total of 17.073348976000 dcy

stealth address amount amount idx
00: d559d34e2f61450a6f21037217ca50a07f58e7a05288fe2a7a437b1fb7376acb 17.073348976000 888468 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": 469520, "vin": [ { "gen": { "height": 469510 } } ], "vout": [ { "amount": 17073348976, "target": { "key": "d559d34e2f61450a6f21037217ca50a07f58e7a05288fe2a7a437b1fb7376acb" } } ], "extra": [ 1, 67, 135, 57, 137, 212, 196, 126, 13, 178, 232, 157, 147, 245, 201, 209, 89, 246, 97, 254, 177, 229, 80, 57, 66, 185, 242, 180, 114, 72, 234, 216, 129, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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