Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16d781c68cf305b1e6a299f5e79029208164448fac9dede22809ef425f6ba6d5

Tx prefix hash: 3c1da55000b5adf9a88f50f75da593e0c89d6a68cfca27b73c2dca34898f81bb
Tx public key: 158e24affb616b1ff89af260219e253b588048d06513ab7e958874d5c2464638
Timestamp: 1583236765 Timestamp [UCT]: 2020-03-03 11:59:25 Age [y:d:h:m:s]: 04:257:15:25:39
Block: 75455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078513 RingCT/type: yes/0
Extra: 01158e24affb616b1ff89af260219e253b588048d06513ab7e958874d5c246463802110000000903d36d11000000000000000000

1 output(s) for total of 345.133454778000 dcy

stealth address amount amount idx
00: 9a969c223d9d0d3e529b7d4462e72a01be029f343b888ef2694ce06d987f11b3 345.133454778000 139396 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": 75465, "vin": [ { "gen": { "height": 75455 } } ], "vout": [ { "amount": 345133454778, "target": { "key": "9a969c223d9d0d3e529b7d4462e72a01be029f343b888ef2694ce06d987f11b3" } } ], "extra": [ 1, 21, 142, 36, 175, 251, 97, 107, 31, 248, 154, 242, 96, 33, 158, 37, 59, 88, 128, 72, 208, 101, 19, 171, 126, 149, 136, 116, 213, 194, 70, 70, 56, 2, 17, 0, 0, 0, 9, 3, 211, 109, 17, 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