Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cea5e8ef21c721796226f0654f5af032fbe24219b369c081bfc3fe39ebd57f6

Tx prefix hash: 46b58b3caee84a3f1738df3792291a3b6d042012aaf27d92f85df0037e5254a9
Tx public key: 208cfdd82cc344d3d78edc703c9f20341d94101e054c8f3a99f5b0445d07c737
Timestamp: 1711505118 Timestamp [UCT]: 2024-03-27 02:05:18 Age [y:d:h:m:s]: 00:360:00:39:06
Block: 987151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257391 RingCT/type: yes/0
Extra: 01208cfdd82cc344d3d78edc703c9f20341d94101e054c8f3a99f5b0445d07c73702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5d6549104355eb8910e5827c98b22ba294b7831553c9d462a1a1d7a0b1ef36 0.600000000000 1447392 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": 987161, "vin": [ { "gen": { "height": 987151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5d6549104355eb8910e5827c98b22ba294b7831553c9d462a1a1d7a0b1ef36" } } ], "extra": [ 1, 32, 140, 253, 216, 44, 195, 68, 211, 215, 142, 220, 112, 60, 159, 32, 52, 29, 148, 16, 30, 5, 76, 143, 58, 153, 245, 176, 68, 93, 7, 199, 55, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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