Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a881fa54b0f59d245c3a4c32e2afa7a3ea48a670aca3bd940eac951623b3ef6c

Tx prefix hash: 36a3cf5e6a60e9c473fc037eed378a0dc6f565ad91e73d1170ca3d264b384f9e
Tx public key: ec21f0a8733c45415d3ae97371fcbea1ead461e62b5e64cd864dfc5771ca5815
Timestamp: 1733174173 Timestamp [UCT]: 2024-12-02 21:16:13 Age [y:d:h:m:s]: 00:118:12:44:13
Block: 1166681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84500 RingCT/type: yes/0
Extra: 01ec21f0a8733c45415d3ae97371fcbea1ead461e62b5e64cd864dfc5771ca5815021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 623b17d0b2a9f204f724e98b7b6d351ec71cc3d414bad1334bf3d1c2910a0319 0.600000000000 1652370 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": 1166691, "vin": [ { "gen": { "height": 1166681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "623b17d0b2a9f204f724e98b7b6d351ec71cc3d414bad1334bf3d1c2910a0319" } } ], "extra": [ 1, 236, 33, 240, 168, 115, 60, 69, 65, 93, 58, 233, 115, 113, 252, 190, 161, 234, 212, 97, 230, 43, 94, 100, 205, 134, 77, 252, 87, 113, 202, 88, 21, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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