Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05a1290bd2e2dec63dd49b2393ee68caf84d992bfb856bd6278855096cf3b6b9

Tx prefix hash: 358026f1fe254659ce20d908234528cc7f120a2225244b96a80aa7c2e683b573
Tx public key: c8ed8da8cc4ed01e462833e888ee37f8d60f3f0bff7ea5ca3e61555111d69f2f
Timestamp: 1735608663 Timestamp [UCT]: 2024-12-31 01:31:03 Age [y:d:h:m:s]: 00:319:17:26:53
Block: 1186824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226030 RingCT/type: yes/0
Extra: 01c8ed8da8cc4ed01e462833e888ee37f8d60f3f0bff7ea5ca3e61555111d69f2f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0e6a9f8adbea982d9692915bd16a5b0ab9fd0bbcfe5b90f02e60bda7dba4791 0.600000000000 1673309 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": 1186834, "vin": [ { "gen": { "height": 1186824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0e6a9f8adbea982d9692915bd16a5b0ab9fd0bbcfe5b90f02e60bda7dba4791" } } ], "extra": [ 1, 200, 237, 141, 168, 204, 78, 208, 30, 70, 40, 51, 232, 136, 238, 55, 248, 214, 15, 63, 11, 255, 126, 165, 202, 62, 97, 85, 81, 17, 214, 159, 47, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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