Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1efe5f2eaa3511a7ae315f98112fc5459e069f70041a951476ab675b06f7dee8

Tx prefix hash: e1f717cdf8c90113f1a8ec7dadc1521b469d6fb425b366b578c9c87e5ef9b59c
Tx public key: 3437e9c9bbd5e5e3b3f5628f34e3c83dbf22803de3bbf9f662db47651161e35e
Timestamp: 1631795418 Timestamp [UCT]: 2021-09-16 12:30:18 Age [y:d:h:m:s]: 03:104:14:22:13
Block: 334909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850529 RingCT/type: yes/0
Extra: 013437e9c9bbd5e5e3b3f5628f34e3c83dbf22803de3bbf9f662db47651161e35e021100000027f29d7abf000000000000000000

1 output(s) for total of 47.677717443000 dcy

stealth address amount amount idx
00: 3f2323c40d4bb74eea933e26cfb4947e0b01374530de62d3c87d9c19e0d86d16 47.677717443000 690550 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": 334919, "vin": [ { "gen": { "height": 334909 } } ], "vout": [ { "amount": 47677717443, "target": { "key": "3f2323c40d4bb74eea933e26cfb4947e0b01374530de62d3c87d9c19e0d86d16" } } ], "extra": [ 1, 52, 55, 233, 201, 187, 213, 229, 227, 179, 245, 98, 143, 52, 227, 200, 61, 191, 34, 128, 61, 227, 187, 249, 246, 98, 219, 71, 101, 17, 97, 227, 94, 2, 17, 0, 0, 0, 39, 242, 157, 122, 191, 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