Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f9ed0d85430cd8f5bb303d443de2c323e6f6359403f4df41866c3638c9395ac

Tx prefix hash: 42cea856ea29be877f7335d64db13cedf42292d0d876c2027cb65087c6a2b022
Tx public key: 326414ed984906e4cf40052687cea93eca04c432d3fc015733c3d5d515091d7d
Timestamp: 1580485836 Timestamp [UCT]: 2020-01-31 15:50:36 Age [y:d:h:m:s]: 05:136:04:39:56
Block: 55948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1249113 RingCT/type: yes/0
Extra: 01326414ed984906e4cf40052687cea93eca04c432d3fc015733c3d5d515091d7d021100000005bd0f9f9f000000000000000000

1 output(s) for total of 400.517849044000 dcy

stealth address amount amount idx
00: 151b4f1573aec33541b29c8e4e7d93d02ddc6da48b99d900ba5ca500b532a5a5 400.517849044000 103192 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": 55958, "vin": [ { "gen": { "height": 55948 } } ], "vout": [ { "amount": 400517849044, "target": { "key": "151b4f1573aec33541b29c8e4e7d93d02ddc6da48b99d900ba5ca500b532a5a5" } } ], "extra": [ 1, 50, 100, 20, 237, 152, 73, 6, 228, 207, 64, 5, 38, 135, 206, 169, 62, 202, 4, 196, 50, 211, 252, 1, 87, 51, 195, 213, 213, 21, 9, 29, 125, 2, 17, 0, 0, 0, 5, 189, 15, 159, 159, 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