Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854e0a63a25410db93d013fb8e3cc82e4797e90e6e80dee30a5e7a3870dc95b9

Tx prefix hash: 07809cefd57f87f7154b2dccdfdba5c36a4f224daee9788dbea358fd7071d941
Tx public key: 7518c8cd485e35bc3b876e46afd80116592854e43cabc875066370063f4b6f37
Timestamp: 1755941040 Timestamp [UCT]: 2025-08-23 09:24:00 Age [y:d:h:m:s]: 00:043:11:40:53
Block: 1352599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30953 RingCT/type: yes/0
Extra: 017518c8cd485e35bc3b876e46afd80116592854e43cabc875066370063f4b6f370211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd93a2dc0ecec2ea0161acf2058b68fa7dc69f6c68ff63a3102d5de246e34299 0.600000000000 1840564 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": 1352609, "vin": [ { "gen": { "height": 1352599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd93a2dc0ecec2ea0161acf2058b68fa7dc69f6c68ff63a3102d5de246e34299" } } ], "extra": [ 1, 117, 24, 200, 205, 72, 94, 53, 188, 59, 135, 110, 70, 175, 216, 1, 22, 89, 40, 84, 228, 60, 171, 200, 117, 6, 99, 112, 6, 63, 75, 111, 55, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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