Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 843fe8dc86aa228cc497f20700c8103949f26461ed2bdc7a358d33fe2c447148

Tx prefix hash: 8678abb1328266de49a6b8198de5a7fc5c41c42bf68b37472b6c4a0bcf44f24c
Tx public key: 980c70f624f716e348d959f5d8bb8317e6e1470b61d902e1097dcb55d0fcec43
Timestamp: 1751305184 Timestamp [UCT]: 2025-06-30 17:39:44 Age [y:d:h:m:s]: 00:134:15:35:29
Block: 1315992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94418 RingCT/type: yes/0
Extra: 01980c70f624f716e348d959f5d8bb8317e6e1470b61d902e1097dcb55d0fcec4302110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fcc8fe77441d4dec835c1ff2a7287d8e064f3ad972f868a7c6578f62605a6cc 0.600000000000 1803649 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": 1316002, "vin": [ { "gen": { "height": 1315992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fcc8fe77441d4dec835c1ff2a7287d8e064f3ad972f868a7c6578f62605a6cc" } } ], "extra": [ 1, 152, 12, 112, 246, 36, 247, 22, 227, 72, 217, 89, 245, 216, 187, 131, 23, 230, 225, 71, 11, 97, 217, 2, 225, 9, 125, 203, 85, 208, 252, 236, 67, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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