Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad88f6aefae66f91436d099f6484d9c8d6b287acb4ebaf2a881f0422be22c690

Tx prefix hash: 90d3cf9346bc21efc1e2ef898195e8bddd9a402f0923191d9547215da1c85f22
Tx public key: e8baaf90973fa6e8c311258a55b85db40f3c37c055ec33b6bfb076e2b45f9096
Timestamp: 1741849408 Timestamp [UCT]: 2025-03-13 07:03:28 Age [y:d:h:m:s]: 00:269:05:41:29
Block: 1238243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190172 RingCT/type: yes/0
Extra: 01e8baaf90973fa6e8c311258a55b85db40f3c37c055ec33b6bfb076e2b45f90960211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482e01174ff357079535338d2e471d9bfb4b575df1fa7c53628d1adf9a61a09e 0.600000000000 1725202 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": 1238253, "vin": [ { "gen": { "height": 1238243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482e01174ff357079535338d2e471d9bfb4b575df1fa7c53628d1adf9a61a09e" } } ], "extra": [ 1, 232, 186, 175, 144, 151, 63, 166, 232, 195, 17, 37, 138, 85, 184, 93, 180, 15, 60, 55, 192, 85, 236, 51, 182, 191, 176, 118, 226, 180, 95, 144, 150, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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