Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd4c3a1edb97a89086a72efc782209c7cafbfbce00fa16d4c089155fc39fc506

Tx prefix hash: ad629da5ce111f92a1a58fd2d6a1c95c14cf67f335c8ecdd98336a64f18ebfcf
Tx public key: 88cc902a77c6f86698fbf6da771bfbc5d5db43f22b2835a6862f7e79234ab399
Timestamp: 1736765864 Timestamp [UCT]: 2025-01-13 10:57:44 Age [y:d:h:m:s]: 00:156:01:22:24
Block: 1196406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111248 RingCT/type: yes/0
Extra: 0188cc902a77c6f86698fbf6da771bfbc5d5db43f22b2835a6862f7e79234ab3990211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 728b44247df8dfe8ffdfe37b95a3fa3a076fd3ea95c81893bf82e83892c60a69 0.600000000000 1683005 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": 1196416, "vin": [ { "gen": { "height": 1196406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "728b44247df8dfe8ffdfe37b95a3fa3a076fd3ea95c81893bf82e83892c60a69" } } ], "extra": [ 1, 136, 204, 144, 42, 119, 198, 248, 102, 152, 251, 246, 218, 119, 27, 251, 197, 213, 219, 67, 242, 43, 40, 53, 166, 134, 47, 126, 121, 35, 74, 179, 153, 2, 17, 0, 0, 0, 3, 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