Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5f87c1a0658b939b9543dd091875609ae229c3854d603b6f3c695bc473d5df

Tx prefix hash: 8a64d07bd8822613a7b59bf5ae05a4d2269c0cf9401bdc32bb44c0cda8ae577a
Tx public key: 1d74ef539da6f4cae13c33069bb85818f0713439c2b3dd912e87cb878971c5de
Timestamp: 1764949024 Timestamp [UCT]: 2025-12-05 15:37:04 Age [y:d:h:m:s]: 00:011:04:50:30
Block: 1427066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8021 RingCT/type: yes/0
Extra: 011d74ef539da6f4cae13c33069bb85818f0713439c2b3dd912e87cb878971c5de021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87fa86629b6139a67fe022c2902f9a18053364966ed6e216de7dfa19b039af2e 0.600000000000 1915765 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": 1427076, "vin": [ { "gen": { "height": 1427066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87fa86629b6139a67fe022c2902f9a18053364966ed6e216de7dfa19b039af2e" } } ], "extra": [ 1, 29, 116, 239, 83, 157, 166, 244, 202, 225, 60, 51, 6, 155, 184, 88, 24, 240, 113, 52, 57, 194, 179, 221, 145, 46, 135, 203, 135, 137, 113, 197, 222, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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