Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aed743c448ab5f6f3be0c226d28aaa44438f9b7989b9c3e8d582f60cd4bbfbf

Tx prefix hash: 00cf87ee621dbbf769d7af41e7b654af33d1b9bd70c1a648a291057cadb58c32
Tx public key: a16b2299e51a2198a953e856e0cdf78344fbf99e79f418ca5062dc409a8f4e2b
Timestamp: 1748474959 Timestamp [UCT]: 2025-05-28 23:29:19 Age [y:d:h:m:s]: 00:176:04:35:45
Block: 1293090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123603 RingCT/type: yes/0
Extra: 01a16b2299e51a2198a953e856e0cdf78344fbf99e79f418ca5062dc409a8f4e2b021100000002df096e52000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e323e0f1a0a74c7d4ccbf7d077b93ee7e447e253351f8f0ee222b1b554bdc43 0.600000000000 1780561 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": 1293100, "vin": [ { "gen": { "height": 1293090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e323e0f1a0a74c7d4ccbf7d077b93ee7e447e253351f8f0ee222b1b554bdc43" } } ], "extra": [ 1, 161, 107, 34, 153, 229, 26, 33, 152, 169, 83, 232, 86, 224, 205, 247, 131, 68, 251, 249, 158, 121, 244, 24, 202, 80, 98, 220, 64, 154, 143, 78, 43, 2, 17, 0, 0, 0, 2, 223, 9, 110, 82, 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