Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc92e04f308bbe91a07643de3c8860e0eef9a1f7c9774ad82578045241c04c3

Tx prefix hash: 8c82a1068946c9dc9ca432032198e169b7ee82d539b7a035ba879d9c36d0553c
Tx public key: e94c99f92976d8b9bf29ecda8612c1e9188b501f3b20f1a018f7f5ae2f697974
Timestamp: 1724836232 Timestamp [UCT]: 2024-08-28 09:10:32 Age [y:d:h:m:s]: 00:226:14:57:13
Block: 1097642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161842 RingCT/type: yes/0
Extra: 01e94c99f92976d8b9bf29ecda8612c1e9188b501f3b20f1a018f7f5ae2f697974021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 643c23fde26af629e1bf6e1cce700604eabf9b8c9bfd8c62bfb9a2ba4f396eed 0.600000000000 1573077 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": 1097652, "vin": [ { "gen": { "height": 1097642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "643c23fde26af629e1bf6e1cce700604eabf9b8c9bfd8c62bfb9a2ba4f396eed" } } ], "extra": [ 1, 233, 76, 153, 249, 41, 118, 216, 185, 191, 41, 236, 218, 134, 18, 193, 233, 24, 139, 80, 31, 59, 32, 241, 160, 24, 247, 245, 174, 47, 105, 121, 116, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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