Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e400d95c7f9486fd0876a75a61dfc492783aaef327dd7ae9706878761b2d231

Tx prefix hash: e3ad7ec27c3d433aac73022b169c3da291aa510a86a155d3db81b4872116b9aa
Tx public key: 49930bbc1f766e0caa85808f8770b6930d1d3bcfcd929172d152dea2f65c00f1
Timestamp: 1720471958 Timestamp [UCT]: 2024-07-08 20:52:38 Age [y:d:h:m:s]: 00:229:07:25:38
Block: 1061483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163772 RingCT/type: yes/0
Extra: 0149930bbc1f766e0caa85808f8770b6930d1d3bcfcd929172d152dea2f65c00f1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 684061c9ab6f4a4a4bbb5b80e91f58fc371fdc53add983b186db34f9811cf24c 0.600000000000 1531974 of 15

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": 1061493, "vin": [ { "gen": { "height": 1061483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "684061c9ab6f4a4a4bbb5b80e91f58fc371fdc53add983b186db34f9811cf24c" } } ], "extra": [ 1, 73, 147, 11, 188, 31, 118, 110, 12, 170, 133, 128, 143, 135, 112, 182, 147, 13, 29, 59, 207, 205, 146, 145, 114, 209, 82, 222, 162, 246, 92, 0, 241, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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