Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9aa97bbd05b5930ea1202e274f527894c0a208183e8894bdc3d2ae48393cc6

Tx prefix hash: 8f47abfed6efde630efd93eb0656c912d8b98ab922e7f6150db541a7a1f0dcac
Tx public key: 9c230f34b2cfbe00c18f6494ccb549215c73d89dcf36e7655bf0ca11f2b75241
Timestamp: 1760482439 Timestamp [UCT]: 2025-10-14 22:53:59 Age [y:d:h:m:s]: 00:030:09:56:31
Block: 1390055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21783 RingCT/type: yes/0
Extra: 019c230f34b2cfbe00c18f6494ccb549215c73d89dcf36e7655bf0ca11f2b75241021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9446cc6709d4495b317e4b61e040e33cd6a151f00890e360b3bd83db4c4caae 0.600000000000 1878286 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": 1390065, "vin": [ { "gen": { "height": 1390055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9446cc6709d4495b317e4b61e040e33cd6a151f00890e360b3bd83db4c4caae" } } ], "extra": [ 1, 156, 35, 15, 52, 178, 207, 190, 0, 193, 143, 100, 148, 204, 181, 73, 33, 92, 115, 216, 157, 207, 54, 231, 101, 91, 240, 202, 17, 242, 183, 82, 65, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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