Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167144158b554f0ead68649a42fbcbb26ff6aed9b55b55860188e2f7c95c6cbf

Tx prefix hash: 81cc828d7007b401e2d6f0fcd6a57189551af8a04b6cc3154e75e1e5f0996262
Tx public key: 0c529061d6cf95e62d74ba4108f07b945b147e0d51aad4f1522b72d7b2a3be21
Timestamp: 1763622776 Timestamp [UCT]: 2025-11-20 07:12:56 Age [y:d:h:m:s]: 00:007:13:06:21
Block: 1416076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5417 RingCT/type: yes/0
Extra: 010c529061d6cf95e62d74ba4108f07b945b147e0d51aad4f1522b72d7b2a3be2102110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a699d857050e4c6d70e7e88364beb2d4e135adcf7464e858dac1038aee28c0e 0.600000000000 1904595 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": 1416086, "vin": [ { "gen": { "height": 1416076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a699d857050e4c6d70e7e88364beb2d4e135adcf7464e858dac1038aee28c0e" } } ], "extra": [ 1, 12, 82, 144, 97, 214, 207, 149, 230, 45, 116, 186, 65, 8, 240, 123, 148, 91, 20, 126, 13, 81, 170, 212, 241, 82, 43, 114, 215, 178, 163, 190, 33, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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