Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73eb9c5f7ba9a5eb2d3872a0bbc42ee4fae37c9f97ea65a58424ae2fe5ef9500

Tx prefix hash: b63d571525ee494e36e19ea8c946574075e5f2de89905e922afee4a16060e832
Tx public key: 023e68142f3b9eb018c7d53770ba75cff923391c179b9845238b40c2296d9d46
Timestamp: 1712170121 Timestamp [UCT]: 2024-04-03 18:48:41 Age [y:d:h:m:s]: 00:235:07:40:10
Block: 992615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168486 RingCT/type: yes/0
Extra: 01023e68142f3b9eb018c7d53770ba75cff923391c179b9845238b40c2296d9d4602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25434b5c9068c51e7c8f04507bef3fb7f9d7cdda70eba1c1cbca1e774dc2efe2 0.600000000000 1452983 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": 992625, "vin": [ { "gen": { "height": 992615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25434b5c9068c51e7c8f04507bef3fb7f9d7cdda70eba1c1cbca1e774dc2efe2" } } ], "extra": [ 1, 2, 62, 104, 20, 47, 59, 158, 176, 24, 199, 213, 55, 112, 186, 117, 207, 249, 35, 57, 28, 23, 155, 152, 69, 35, 139, 64, 194, 41, 109, 157, 70, 2, 17, 0, 0, 0, 5, 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