Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07e3fdd85fd5766bd094513fe60f3250ee2cce11b595d9cd7999a6e26e79d555

Tx prefix hash: 82675158a851c225f0c06d0f65d3c44d2111a6decc7d2099f181f127f5cfb030
Tx public key: c5da08fa7f54f361217eacd0d943943a784dc4b084a8ed28a5bc5c82c12269b7
Timestamp: 1709506864 Timestamp [UCT]: 2024-03-03 23:01:04 Age [y:d:h:m:s]: 01:037:13:47:52
Block: 970567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287855 RingCT/type: yes/0
Extra: 01c5da08fa7f54f361217eacd0d943943a784dc4b084a8ed28a5bc5c82c12269b702110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cad4cf26b35324035a67a0490ef906c11f3ae5b47a0d0f38ea81c008bc86593d 0.600000000000 1430426 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": 970577, "vin": [ { "gen": { "height": 970567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cad4cf26b35324035a67a0490ef906c11f3ae5b47a0d0f38ea81c008bc86593d" } } ], "extra": [ 1, 197, 218, 8, 250, 127, 84, 243, 97, 33, 126, 172, 208, 217, 67, 148, 58, 120, 77, 196, 176, 132, 168, 237, 40, 165, 188, 92, 130, 193, 34, 105, 183, 2, 17, 0, 0, 0, 15, 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