Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2aa00d843f9801076de5546da396df236e12d4f652353d3a1bc85aa28639ff

Tx prefix hash: 173f940b582e3517cf998c9265bbc91e37b4d49414e23d5c9d64dc7b1601b0a1
Tx public key: 253de16d3f0879befd936f1c9913e6dd0ff1de9fa5111b40cd26719ca7b05f49
Timestamp: 1578931504 Timestamp [UCT]: 2020-01-13 16:05:04 Age [y:d:h:m:s]: 04:362:20:00:40
Block: 44785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148802 RingCT/type: yes/0
Extra: 01253de16d3f0879befd936f1c9913e6dd0ff1de9fa5111b40cd26719ca7b05f490211000000078a2ee0d9000000000000000000

1 output(s) for total of 436.123555970000 dcy

stealth address amount amount idx
00: fe22cac43c4f815e904cd4205b7893a360e59ae00a46db03a5900a86ed51e0a9 436.123555970000 81599 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": 44795, "vin": [ { "gen": { "height": 44785 } } ], "vout": [ { "amount": 436123555970, "target": { "key": "fe22cac43c4f815e904cd4205b7893a360e59ae00a46db03a5900a86ed51e0a9" } } ], "extra": [ 1, 37, 61, 225, 109, 63, 8, 121, 190, 253, 147, 111, 28, 153, 19, 230, 221, 15, 241, 222, 159, 165, 17, 27, 64, 205, 38, 113, 156, 167, 176, 95, 73, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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