Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc899bd1327e5d4b6ebfe416678a68cbc340f46a6cac9dc335a86e4cfce71839

Tx prefix hash: eca1d63f8f03062e5a202930542b52b7319267b9e560ef1bc04cd2886d85bfce
Tx public key: c31fa1e220393f148f92ac4ab6aef47a07c09e6e2e9773a3e761d09e0c251624
Timestamp: 1741653665 Timestamp [UCT]: 2025-03-11 00:41:05 Age [y:d:h:m:s]: 00:293:21:40:20
Block: 1236619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207835 RingCT/type: yes/0
Extra: 01c31fa1e220393f148f92ac4ab6aef47a07c09e6e2e9773a3e761d09e0c251624021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56fb677606d37caf64bbf5dbfd811eb8e3dbc2ce4944c95c755681226d90c109 0.600000000000 1723566 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": 1236629, "vin": [ { "gen": { "height": 1236619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56fb677606d37caf64bbf5dbfd811eb8e3dbc2ce4944c95c755681226d90c109" } } ], "extra": [ 1, 195, 31, 161, 226, 32, 57, 63, 20, 143, 146, 172, 74, 182, 174, 244, 122, 7, 192, 158, 110, 46, 151, 115, 163, 231, 97, 208, 158, 12, 37, 22, 36, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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